Techniques for reporting timing differences in multiple connectivity wireless communications

ABSTRACT

Certain aspects of the present disclosure relate to reporting difference in timing between cells using multiple connectivity in a wireless network. A first connection served by at least a first cell and a second connection served by at least a second cell to facilitate communicating with at least the first cell and at least the second cell are established. A reporting configuration specifying one or more parameters related to reporting a timing difference between cells is received. A timing difference between at least the first cell and at least the second cell is determined, and the timing difference is reported to at least the first cell over the first connection or to at least the second cell over the second connection. This can facilitate scheduling time aligned operations over the first and second cells, or related cell groups, in multiple connectivity.

CLAIM OF PRIORITY UNDER 35 U.S.C. § 119

The present Application for Patent claims priority to ProvisionalApplication No. 62/023,717 entitled “TECHNIQUES FOR REPORTING TIMINGDIFFERENCES BETWEEN MULTIPLE CELLS OR CELL GROUPS IN MULTIPLECONNECTIVITY WIRELESS COMMUNICATIONS” filed Jul. 11, 2014, which isassigned to the assignee hereof and hereby expressly incorporated in itsentirety by reference herein.

FIELD OF THE DISCLOSURE

The present disclosure, for example, relates to wireless communicationsystems, and more particularly to techniques for reporting timingdifferences in multiple connectivity wireless communications.

BACKGROUND OF THE DISCLOSURE

Wireless communication networks are widely deployed to provide variouscommunication services such as voice, video, packet data, messaging,broadcast, etc. These wireless networks may be multiple-access networkscapable of supporting multiple users by sharing the available networkresources. Examples of such multiple-access networks include CodeDivision Multiple Access (CDMA) networks, Time Division Multiple Access(TDMA) networks, Frequency Division Multiple Access (FDMA) networks,Orthogonal FDMA (OFDMA) networks, and Single-Carrier FDMA (SC-FDMA)networks.

A wireless communication network may include a number of base stations(e.g., eNodeBs) that can support communication for a number of userequipments (UEs). A UE may communicate with a base station via thedownlink and uplink. The downlink (or forward link) refers to thecommunication link from the base station to the UE, and the uplink (orreverse link) refers to the communication link from the UE to the basestation.

In multiple connectivity, the UE can be configured to communicate withmultiple cells or cell groups configured by multiple base stations usingmultiple links. In this configuration, the multiple cells or cell groupsmay not be synchronized in time, which may result in failure of certainprocedures that may benefit from timing alignment among the cells orcell groups. Such procedures may include defining measurement gapsduring which a UE can tune away from the multiple cells or cell groupsto measure cells of other frequencies or radio access technologies,discontinuous receive (DRX) mode operations where the UE receiver isactive only during certain durations to lower power consumption, etc. Ifthe multiple cell or cell groups are not time aligned for suchprocedures, however, the UE transceiver may miss signals from one cellor cell group during a measurement gap defined by another cell or cellgroup or in an idle period for a DRX mode defined by another cell orcell group.

SUMMARY OF THE DISCLOSURE

Aspects of the present disclosure relate generally to wirelesscommunications, and more particularly, to techniques for determining andreporting timing differences between multiple cells or cell groups inmultiple connectivity wireless communications. For example, techniquesfor reporting timing differences when communicating with multiple cellsconfigured by multiple base stations are described herein.

In accordance with an aspect, a method for reporting difference intiming between cells using multiple connectivity in a wireless networkis provided. The method includes establishing a first connection servedby at least a first cell, and establishing a second connection served byat least a second cell. The method also includes receiving a reportingconfiguration specifying one or more parameters related to reporting atiming difference between cells, determining a timing difference betweenat least the first cell and at least the second cell, and reporting thetiming difference to at least the first cell over the first connectionor to at least the second cell over the second connection based at leastin part on the reporting configuration.

The method may also include wherein the first connection is with amaster cell group comprising at least the first cell, and the secondconnection is with a secondary cell group comprising at least the secondcell. The method may further include wherein receiving the reportingconfiguration comprising receiving the reporting configuration from atleast the first cell or at least the second cell. Additionally, themethod may include wherein reporting the timing difference is based atleast in part on detecting expiration of a periodic timer, wherein theone or more parameters relate to the periodic timer. Further, the methodmay include wherein reporting the timing difference is based at least inpart on determining that the timing difference differs from an assumedtiming difference by at least a threshold, wherein the one or moreparameters relate to the assumed timing difference or the threshold. Themethod may also include wherein reporting the timing difference is basedat least in part on determining that the timing difference differs froma previously reported timing difference by at least a threshold, whereinthe one or more parameters relate to the threshold.

The method may also include wherein reporting the timing difference isbased at least in part on determining that the timing differencecorresponds to an offset in subframe alignment that is outside of arange corresponding to a possible timing accuracy where a previouslyreported timing difference corresponded to a previous offset in subframealignment that was inside of the range corresponding to the possibletiming accuracy. Further, the method may include wherein reporting thetiming difference is based at least in part on determining that thetiming difference corresponds to an offset in subframe alignment that isinside of a range corresponding to a possible timing accuracy where apreviously reported timing difference corresponded to a previous offsetin subframe alignment that was outside of the range corresponding to thepossible timing accuracy. Additionally, the method may include whereinreporting the timing difference is based at least in part on detectingexpiration of a prohibit timer. The method may also include configuringone or more parameters for communicating over the first connection orthe second connection based at least in part on the timing difference.Additionally, the method may include wherein the one or more parameterscorrespond to measurement gaps defined for the first connection or thesecond connection. Furthermore, the method may include receiving aconnection reconfiguration message to configure the second connectionserved by at least the second cell, wherein reporting the timingdifference is based at least in part on receiving the reportingconfiguration, and wherein establishing the second connection includesconfiguring the second connection based at least in part on receivingthe connection reconfiguration message and reporting the timingdifference.

In another example, an apparatus for reporting difference in timingbetween cells using multiple connectivity in a wireless network isprovided. The apparatus includes a communicating component configured toestablish a first connection served by at least a first cell andestablish a second connection served by at least a second cell tofacilitate communicating with at least the first cell and at least thesecond cell. The apparatus also includes a timing difference triggeringcomponent configured to receive a reporting configuration specifying oneor more parameters related to reporting a timing difference betweencells, a timing difference determining component configured to determinea timing difference between at least the first cell and at least thesecond cell, and a timing difference reporting component configured toreport the timing difference to at least the first cell over the firstconnection or to at least the second cell over the second connectionbased at least in part on the reporting configuration.

In addition, the apparatus may include wherein the first connection iswith a master cell group comprising at least the first cell, and thesecond connection is with a secondary cell group comprising at least thesecond cell. The apparatus may also include wherein the timingdifference triggering component is configured to receive the reportingconfiguration from at least the first cell or at least the second cell.Moreover, the apparatus may include wherein the timing differencereporting component is configured to report the timing difference basedat least in part on the timing difference triggering component detectingexpiration of a periodic timer, wherein the one or more parametersrelate to the periodic timer. The apparatus may also include wherein thetiming difference reporting component is configured to report the timingdifference based at least in part on the timing difference triggeringcomponent determining that the timing difference differs from an assumedtiming difference by at least a threshold, wherein the one or moreparameters relate to the assumed timing difference or the threshold. Inaddition, the apparatus may include wherein the timing differencereporting component is configured to report the timing difference basedat least in part on the timing difference triggering componentdetermining that the timing difference differs from a previouslyreported timing difference by at least a threshold, wherein the one ormore parameters relate to the threshold.

Additionally, the apparatus may include wherein the timing differencereporting component is configured to report the timing difference basedat least in part on the timing difference triggering componentdetermining that the timing difference corresponds to an offset insubframe alignment that is outside of a range corresponding to apossible timing accuracy where a previously reported timing differencecorresponded to a previous offset in subframe alignment that was insideof the range corresponding to the possible timing accuracy. Theapparatus may also include wherein the timing difference reportingcomponent is configured to report the timing difference based at leastin part on the timing difference triggering component determining thatthe timing difference corresponds to an offset in subframe alignmentthat is inside of a range corresponding to a possible timing accuracywhere a previously reported timing difference corresponded to a previousoffset in subframe alignment that was outside of the range correspondingto the possible timing accuracy. Further, the apparatus may includewherein the timing difference reporting component is configured toreport the timing difference based at least in part on the timingdifference triggering component detecting expiration of the prohibittimer. The apparatus may also include wherein the communicatingcomponent is further configured to configure one or more parameters forcommunicating over the first connection or the second connection basedat least in part on the timing difference. Additionally, the apparatusmay include wherein the one or more parameters correspond to measurementgaps defined for the first connection or the second connection. Theapparatus may further include a connection configuring componentconfigured to receive a connection reconfiguration message to configurethe second connection served by at least the second cell, wherein thetiming difference reporting component is configured to report the timingdifference based at least in part on receiving the reportingconfiguration, and wherein the communicating component is configured toestablish the second connection at least in part by configuring thesecond connection based at least in part on receiving the connectionreconfiguration message and reporting the timing difference.

In another example, an apparatus for reporting difference in timingbetween cells using multiple connectivity in a wireless network isprovided. The apparatus includes means for establishing a firstconnection served by at least a first cell, and means for establishing asecond connection served by at least a second cell to facilitatecommunicating with at least the first cell and at least the second cell.The apparatus also includes means for receiving a reportingconfiguration specifying one or more parameters related to reporting atiming difference between cells, means for determining a timingdifference between at least the first cell and at least the second cell,and means for reporting the timing difference to at least the first cellover the first connection or to at least the second cell over the secondconnection based at least in part on the reporting configuration.

The apparatus can also include wherein the first connection is with amaster cell group comprising at least the first cell, and the secondconnection is with a secondary cell group comprising at least the secondcell. The apparatus may further include wherein the means for receivingreceives the reporting configuration from at least the first cell or atleast the second cell.

In another example, a computer-readable storage medium comprisingcomputer-executable code for reporting difference in timing betweencells using multiple connectivity in a wireless network is provided. Thecode includes code for establishing a first connection served by atleast a first cell, and code for establishing a second connection servedby at least a second cell to facilitate communicating with at least thefirst cell and at least the second cell. The code further includes codefor receiving a reporting configuration specifying one or moreparameters related to reporting a timing difference between cells, codefor determining a timing difference between at least the first cell andat least the second cell, and code for reporting the timing differenceto at least the first cell over the first connection or to at least thesecond cell over the second connection based at least in part on thereporting configuration.

The computer-readable storage medium may also include wherein the firstconnection is with a master cell group comprising at least the firstcell, and the second connection is with a secondary cell groupcomprising at least the second cell. The computer-readable storagemedium may further include wherein the code for receiving receives thereporting configuration from at least the first cell or at least thesecond cell.

Various aspects and features of the disclosure are described in furtherdetail below with reference to various examples thereof as shown in theaccompanying drawings. While the present disclosure is described belowwith reference to various examples, it should be understood that thepresent disclosure is not limited thereto. Those of ordinary skill inthe art having access to the teachings herein will recognize additionalimplementations, modifications, and examples, as well as other fields ofuse, which are within the scope of the present disclosure as describedherein, and with respect to which the present disclosure may be ofsignificant utility.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to facilitate a fuller understanding of the present disclosure,reference is now made to the accompanying drawings, in which likeelements are referenced with like numerals. These drawings should not beconstrued as limiting the present disclosure, but are intended to beillustrative only.

FIG. 1 is a block diagram conceptually illustrating an example of awireless communications system, in accordance with various aspects ofthe present disclosure.

FIG. 2 is a block diagram conceptually illustrating examples of aneNodeB and a UE configured in accordance with various aspects of thepresent disclosure.

FIG. 3 is a block diagram conceptually illustrating an aggregation ofradio access technologies at a UE, in accordance with various aspects ofthe present disclosure.

FIG. 4 is a block diagram conceptually illustrating an example of datapaths between a UE and a PDN, in accordance with various aspects of thepresent disclosure.

FIG. 5 is a diagram conceptually illustrating multiple connectivitycarrier aggregation, in accordance with various aspects of the presentdisclosure.

FIG. 6 is a block diagram conceptually illustrating an example of a UEand components configured in accordance with various aspects of thepresent disclosure.

FIG. 7 illustrates example timing differences between network entitiesin a wireless network, in accordance with various aspects of the presentdisclosure.

FIG. 8 is a flowchart illustrating a method for reporting timingdifference, in accordance with various aspects of the presentdisclosure.

FIG. 9 is a flowchart illustrating a method for configuring a connectionin a wireless network, in accordance with various aspects of the presentdisclosure.

FIG. 10 is a block diagram conceptually illustrating an example of anetwork entity and components configured in accordance with variousaspects of the present disclosure.

FIG. 11 is a flowchart illustrating a method for configuring aconnection based on a reported timing difference in accordance withvarious aspects of the present disclosure.

FIG. 12 is a flowchart illustrating a method for configuring aconnection based on receiving a timing difference, in accordance withvarious aspects of the present disclosure.

FIG. 13 is a block diagram conceptually illustrating an example hardwareimplementation for an apparatus employing a processing system configuredin accordance with various aspects of the present disclosure.

DETAILED DESCRIPTION

The detailed description set forth below, in connection with theappended drawings, is intended as a description of variousconfigurations and is not intended to represent the only configurationsin which the concepts described herein may be practiced. The detaileddescription includes specific details for the purpose of providing athorough understanding of the various concepts. However, it will beapparent to those skilled in the art that these concepts may bepracticed without these specific details. In some instances, well-knownstructures and components are shown in block diagram form in order toavoid obscuring such concepts.

Various techniques including methods, apparatuses, devices, and systemsare described for determining and reporting timing difference betweenmultiple cells or cell groups in a multiple connectivity wirelesscommunication mode. In some aspects, a wireless device (e.g., userequipment (UE)) can communicate with the multiple cells configured byone or more network entities using multiple connectivity wirelesscommunication modes, which may include receiving granted resources fromeach of the multiple cells, over which the wireless device cancommunicate in accessing a wireless network. In some aspects, a wirelessdevice may receive first configuration information to communicate with afirst primary cell (e.g., a master cell group (MCG)/primary cell group(PCG) primary cell, also referred to herein as a PCell_(MCG)) of a firstnetwork entity. The wireless device may also receive secondconfiguration information to communicate with a second primary cell(e.g., a secondary cell group (SCG) primary cell, also referred toherein as a PCell_(SCG)) of a second network entity. In the case ofmultiple connectivity, the PCells may be configured by different eNodeBs(e.g., a master eNodeB/primary eNodeB, also referred to herein as anMeNodeB, that provides the PCell, and a secondary eNodeB, also referredto herein as an SeNodeB, that provides the PCell_(SCG)). The PCells maybe configured to operate respective cell groups (e.g., MCG and/or SCG),which may include one or more cells (e.g., the PCell and one or moreSCells). For example, one or more cells in a cell group may operate in adifferent frequency band and/or may include one or more componentcarriers (CCs). It is to be appreciated that the first network entitymay be non-collocated with the second network entity or collocated withthe first network entity in some examples.

In either case, each of the first primary cell and the second primarycell (or respective cell groups) may not be synchronized in time withone another. Thus, the UE can report a timing difference and/or relatedinformation to one or more of the first primary cell, second primarycell (or respective cell groups), or other network entities tofacilitate performing certain operations that may benefit from timingalignment among the cells or cell groups, such as determiningmeasurement gaps, communicating using a discontinuous receive (DRX)mode, etc. The UE may report the timing difference based on a reportingconfiguration. A reporting configuration may refer to a configurationstored by the UE, which may be received from one or more networkentities (e.g., one or more eNodeBs) or otherwise provisioned to the UE.The reporting configuration can specify one or more parameters relatedto conditions for triggering timing difference determination among thecells or cell groups and/or reporting of the timing difference. Thus, asdescribed further herein, the reporting configuration can indicate atype of a trigger for determining and/or reporting the timing difference(e.g., a periodic timer, a comparison between timing differences, adetermination of subframes affected by the timing difference, a prohibittimer, etc.), one or more parameters related to the trigger (e.g., timervalues, thresholds for comparing differences, etc.), and/or the like. Insome examples, the UE may also suspend such operations until the timingdifference is reported, in some examples, to ensure that properalignment may be achieved among the cells or cell groups based on thetiming difference.

The techniques described herein may be used for various wirelesscommunication networks such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA andother networks. The terms “network” and “system” are often usedinterchangeably. A CDMA network may implement a radio technology such asUniversal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includesWideband CDMA (WCDMA) and other variants of CDMA. cdma2000 coversIS-2000, IS-95 and IS-856 standards. A TDMA network may implement aradio technology such as Global System for Mobile Communications (GSM).An OFDMA network may implement a radio technology such as Evolved UTRA(E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16(WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part ofUMTS. 3GPP LTE and LTE-Advanced (LTE-A) are new releases of UMTS thatuse E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described indocuments from an organization named “3rd Generation PartnershipProject” (3GPP). cdma2000 and UMB are described in documents from anorganization named “3rd Generation Partnership Project 2” (3GPP2). Thetechniques described herein may be used for the wireless networks andradio technologies mentioned above as well as other wireless networksand radio technologies. For clarity, certain aspects of the techniquesare described below for LTE, and LTE terminology is used in much of thedescription below.

FIG. 1 is a block diagram conceptually illustrating an example of awireless communications system 100, in accordance with various aspectsof the present disclosure. The wireless communications system 100includes eNodeBs (or cells) 105, user equipment (UEs) 115, and a corenetwork 130. The eNodeBs 105 may communicate with the UEs 115 under thecontrol of a base station controller (not shown), which may be part ofthe core network 130 or the eNodeBs 105 in various embodiments. One ormore UEs 115 can include a communicating component 640 for determiningand/or reporting timing differences among various eNodeBs 105 servingthe UE 115 in multiple connectivity. One or more eNodeBs 105 can includea communicating component 1040 for receiving reported timing differencesfrom the UE 115 with other eNodeBs for determining scheduling of one ormore operations for the UE 115. The eNodeBs 105 may communicate controlinformation and/or user data with the core network 130 through firstbackhaul links 132. In embodiments, the eNodeBs 105 may communicate,either directly or indirectly, with each other over second backhaullinks 134, which may be wired or wireless communication links. Thewireless communications system 100 may support operation on multiplecarriers (waveform signals of different frequencies). Multi-carriertransmitters can transmit modulated signals simultaneously on themultiple carriers. For example, each communication link 125 may be amulti-carrier signal modulated according to the various radiotechnologies described above. Each modulated signal may be sent on adifferent carrier and may carry control information (e.g., referencesignals, control channels, etc.), overhead information, data, etc. Thewireless communications system 100 may also support operation onmultiple flows at the same time. In some aspects, the multiple flows maycorrespond to multiple wireless wide area networks (WWANs) or cellularflows. In other aspects, the multiple flows may correspond to acombination of WWANs or cellular flows and wireless local area networks(WLANs) or Wi-Fi flows.

The eNodeBs 105 may wirelessly communicate with the UEs 115 via one ormore base station antennas. Each of the eNodeBs 105 sites may providecommunication coverage for a respective geographic coverage area 110. Insome embodiments, eNodeBs 105 may be referred to as a base transceiverstation, a radio base station, an access point, a radio transceiver, abasic service set (BSS), an extended service set (ESS), a NodeB, eNodeB,Home NodeB, a Home eNodeB, or some other suitable terminology. Thegeographic coverage area 110 for a eNodeB 105 may be divided intosectors making up only a portion of the coverage area (not shown). Thewireless communications system 100 may include eNodeBs 105 of differenttypes (e.g., macro, micro, and/or pico base stations). There may beoverlapping coverage areas for different technologies.

In implementations, the wireless communications system 100 is anLTE/LTE-A network communication system. In LTE/LTE-A networkcommunication systems, the terms evolved Node B (eNodeB) may begenerally used to describe the eNodeBs 105. The wireless communicationssystem 100 may be a Heterogeneous LTE/LTE-A network in which differenttypes of eNodeBs provide coverage for various geographical regions. Forexample, each eNodeB 105 may provide communication coverage for a macrocell, a pico cell, a femto cell, and/or other types of cell. A macrocell may cover a relatively large geographic area (e.g., severalkilometers in radius) and may allow unrestricted access by UEs 115 withservice subscriptions with the network provider. A pico cell may cover arelatively smaller geographic area (e.g., buildings) and may allowunrestricted access by UEs 115 with service subscriptions with thenetwork provider. A femto cell may cover a relatively small geographicarea (e.g., a home) and, in addition to unrestricted access, may alsoprovide restricted access by UEs 115 having an association with thefemto cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115for users in the home, and the like). An eNodeB 105 for a macro cell maybe referred to as a macro eNodeB. An eNodeB 105 for a pico cell may bereferred to as a pico eNodeB. And, an eNodeB 105 for a femto cell may bereferred to as a femto eNodeB or a home eNodeB. An eNodeB 105 maysupport one or multiple (e.g., two, three, four, and the like) cells.The wireless communications system 100 may support use of LTE and WLANor Wi-Fi by one or more of the UEs 115.

The core network 130 may communicate with the eNodeBs 105 or othereNodeBs 105 via first backhaul links 132 (e.g., S1 interface, etc.). TheeNodeBs 105 may also communicate with one another, e.g., directly orindirectly via second backhaul links 134 (e.g., X2 interface, etc.)and/or via the first backhaul links 132 (e.g., through core network130). The wireless communications system 100 may support synchronous orasynchronous operation. For synchronous operation, the eNodeBs 105 mayhave similar frame timing, and transmissions from different eNodeBs 105may be approximately aligned in time. For asynchronous operation, theeNodeBs 105 may have different frame timing, and transmissions fromdifferent eNodeBs 105 may not be aligned in time. The techniquesdescribed herein may be used for either synchronous or asynchronousoperations.

The UEs 115 may be dispersed throughout the wireless communicationssystem 100, and each UE 115 may be stationary or mobile. A UE 115 mayalso be referred to by those skilled in the art as a mobile station, asubscriber station, a mobile unit, a subscriber unit, a wireless unit, aremote unit, a mobile device, a wireless device, a wirelesscommunications device, a remote device, a mobile subscriber station, anaccess terminal, a mobile terminal, a wireless terminal, a remoteterminal, a handset, a user agent, a mobile client, a client, or someother suitable terminology. A UE 115 may be a cellular phone, a personaldigital assistant (PDA), a wireless modem, a wireless communicationdevice, a handheld device, a tablet computer, a laptop computer, acordless phone, a wireless local loop (WLL) station, or the like. A UE115 may be able to communicate with macro eNodeBs, pico eNodeBs, femtoeNodeBs, relays, and the like.

The communication links 125 shown in the wireless communications system100 may include uplink (UL) transmissions from a UE 115 to an eNodeB105, and/or downlink (DL) transmissions, from an eNodeB 105 to a UE 115.The downlink transmissions may also be called forward link transmissionswhile the uplink transmissions may also be called reverse linktransmissions.

In certain aspects of the wireless communications system 100, a UE 115may be configured to support carrier aggregation (CA) or multipleconnectivity wireless communications with two or more cells provided byone or more eNodeBs 105. The eNodeBs 105 that are used for CA/multipleconnectivity wireless communications may be collocated or may beconnected through fast connections and/or non-collocated. In eithercase, coordinating the aggregation of component carriers (CCs) forwireless communications between the UE 115 and the eNodeBs 105 may becarried out more easily because information can be readily sharedbetween the various cells being used to perform the carrier aggregation.When the eNodeBs 105 that are used for carrier aggregation arenon-collocated (e.g., far apart or do not have a high-speed connectionbetween them), then coordinating the aggregation of component carriersmay involve additional aspects. For example, in carrier aggregation fordual connectivity (e.g., UE 115 connected to two non-collocated eNodeBs105), the UE 115 may receive configuration information to communicatewith a first eNodeB 105 (e.g., SeNodeB or SeNB) through a primary cellof the first eNodeB 105. The first eNodeB 105 may include a group ofcells referred to as a secondary cell group or SCG, which includes oneor more secondary cells and the primary cell or PCell_(SCG) of the firsteNodeB 105. The UE 115 may also receive configuration information tocommunicate with a second eNodeB 105 (e.g., MeNodeB or MeNB) through asecond primary cell of the second eNodeB 105. The second eNodeB 105 mayinclude a group of cells referred to as a master cell group or MCG,which includes one or more secondary cells and the primary cell orPCell_(MCG) of the second eNodeB 105.

In certain aspects of the wireless communications system 100, carrieraggregation for dual connectivity may involve having a secondary eNodeB105 (e.g., SeNodeB or SeNB) be configured to operate one of its cells asa PCell_(SCG). The secondary eNodeB 105 may transmit, to a UE 115,configuration information through the PCell_(SCG) for the UE 115 tocommunicate with the secondary eNodeB 105 while the UE 115 is incommunication with a master eNodeB 105 (e.g., MeNodeB or MeNB). Themaster eNodeB 105 may transmit, to the same UE 115, configurationinformation via its PCell for that UE 115 to communicate with the othereNodeB 105. The two eNodeBs 105 may be non-collocated.

In examples described herein, UE 115 can be configured for determining atiming difference between the MCG and SCG and/or reporting the timingdifference to one or more eNodeBs (e.g., eNodeBs 105) of the MCG, SCG,or other network entities, as described further herein. For example, theUE 115 can acquire system information from eNodeBs 105 of the MCG and/orSCG (e.g., one or more master information blocks (MIB)) from whichtiming of the eNodeB 105 or related cells or cell groups can bedetermined. Thus, the UE 115 can synchronize to one or more eNodeBs 105of the MCG and one or more eNodeBs 105 of the SCG based on the systeminformation, and can determine a timing difference between the MCG andSCG based on the timing used to synchronize with the eNodeBs 105.Accordingly, the UE 115 can report the determined timing difference tothe network (e.g., via MCG and/or SCG or related eNodeBs 105), and thetiming difference may be used to align resources for certain operations(e.g., measurement gaps, DRX-on duration during which resources forreceiving communications are to be turned on, etc.). Without suchalignment, the SCG may separately schedule the UE 115 for the operationsinconsistently with the eNodeBs 105, which may result in an unnecessaryutilization of resources for the operations.

For example, eNodeBs 105 of the MCG and SCG may not be aligned intiming, which can result in the MCG and SCG having different subframes(e.g. in different system frame numbers (SFN) or otherwise) positionedat similar times and/or having a different alignment of subframeboundaries. Accordingly, certain configurations that assume timingalignment, such as measurement gaps, DRX-on durations, etc., may notperform as desired unless the timing difference is provided to at leastone of the eNodeBs 105 in at least one of the cell groups that schedulesthe UE 115 for such operations. Thus, for example UE 115 can determineand report the timing difference, and at least one of the eNodeBs 105can use the reported timing difference in aligning resources assignedfor the configurations with the other eNodeB 105, which can includealigning subframes for the configurations, aligning timing of the eNodeBsuch to use the same SFN or align subframes such that system framesbegin at the same time as the other eNodeB 105, and/or the like. It isto be appreciated that the where the subframe boundaries are not alignedand/or where the timing difference measured and reported by the UE 115may include some degree of inaccuracy, the eNodeB 105 aligning timingcan determine a number of additional subframes to schedule in aligningthe timing for the certain configurations based on the misalignment ofsubframe boundaries and/or potential inaccuracy of the received report,as described further herein.

Moreover, the UE 115 can determine to measure and/or report timingdifference between the eNodeBs based on one or more triggers, such as aperiodic time trigger, a measured difference in timing beyond an assumedtiming or beyond a previously reported timing difference exceeding athreshold, a determination of certain subframes being impacted by atiming change, an expiration of a prohibit timer prohibiting measuringand reporting timing difference, etc. In addition, in one example, wherethe UE 115 initiates communications with a first eNodeB 105, the UE 115can delay establishing communications with a second eNodeB 105 until atiming difference between the first and second eNodeBs is reported,until a confirmation of receiving the report or otherwise that thecommunications with the second eNodeB 105 can be established isreceived, etc.

FIG. 2 is a block diagram conceptually illustrating examples of aneNodeB 210 and a UE 250 configured in accordance with an aspect of thepresent disclosure. For example, the eNodeB 210 and the UE 250 of asystem 200, as shown in FIG. 2, may be one of the eNodeBs and one of theUEs in FIG. 1, respectively. Thus, for example, UE 250 can include acommunicating component 640 for determining and/or reporting timingdifferences among various eNodeBs 210 serving the UE 250 in multipleconnectivity. The eNodeB 210 can include a communicating component 1040for receiving reported timing differences from the UE 250 with othereNodeBs for determining scheduling of one or more operations for the UE250. In some aspects, the eNodeB 210 may support multiple connectivity(e.g., dual connectivity), carrier aggregation, etc. The eNodeB 210 maybe an MeNodeB having one of the cells in its MCG configured as aPCell_(MCG) or an SeNodeB having one of its cells in its SCG configuredas a PCell_(SCG). In some aspects, the UE 250 may also support multipleconnectivity carrier aggregation. The UE 250 may receive configurationinformation from the eNodeB 210 via the PCell_(MCG) and/or thePCell_(SCG). The eNodeB 210 may be equipped with antennas 234 _(1-t),and the UE 250 may be equipped with antennas 252 _(1-r), wherein t and rare integers greater than or equal to one.

At the eNodeB 210, a eNodeB transmit processor 220 may receive data froma eNodeB data source 212 and control information from a eNodeBcontroller/processor 240. The control information may be carried on thePBCH, PCFICH, physical hybrid automatic repeat/request (HARQ) indicatorchannel (PHICH), PDCCH, etc. The data may be carried on the PDSCH, etc.The eNodeB transmit processor 220 may process (e.g., encode and symbolmap) the data and control information to obtain data symbols and controlsymbols, respectively. The eNodeB transmit processor 220 may alsogenerate reference symbols, e.g., for the PSS, SSS, and cell-specificreference signal (RS). A eNodeB transmit (TX) multiple-inputmultiple-output (MIMO) processor 230 may perform spatial processing(e.g., precoding) on the data symbols, the control symbols, and/or thereference symbols, if applicable, and may provide output symbol streamsto the eNodeB modulators/demodulators (MODs/DEMODs) 232 _(1-t). EacheNodeB modulator/demodulator 232 may process a respective output symbolstream (e.g., for OFDM, etc.) to obtain an output sample stream. EacheNodeB modulator/demodulator 232 may further process (e.g., convert toanalog, amplify, filter, and upconvert) the output sample stream toobtain a downlink signal. Downlink signals from modulators/demodulators232 _(1-t) may be transmitted via the antennas 234 _(1-t), respectively.

At the UE 250, the UE antennas 252 _(1-r) may receive the downlinksignals from the eNodeB 210 and may provide received signals to the UEmodulators/demodulators (MODs/DEMODs) 254 _(1-r), respectively. Each UEmodulator/demodulator 254 may condition (e.g., filter, amplify,downconvert, and digitize) a respective received signal to obtain inputsamples. Each UE modulator/demodulator 254 may further process the inputsamples (e.g., for OFDM, etc.) to obtain received symbols. A UE MIMOdetector 256 may obtain received symbols from all the UEmodulators/demodulators 254 _(1-r), and perform MIMO detection on thereceived symbols if applicable, and provide detected symbols. A UEreception processor 258 may process (e.g., demodulate, deinterleave, anddecode) the detected symbols, provide decoded data for the UE 250 to aUE data sink 260, and provide decoded control information to a UEcontroller/processor 280.

On the uplink, at the UE 250, a UE transmit processor 264 may receiveand process data (e.g., for the PUSCH) from a UE data source 262 andcontrol information (e.g., for the PUCCH) from the UEcontroller/processor 280. The UE transmit processor 264 may alsogenerate reference symbols for a reference signal. The symbols from theUE transmit processor 264 may be precoded by a UE TX MIMO processor 266if applicable, further processed by the UE modulator/demodulators 254_(1-r) (e.g., for SC-FDM, etc.), and transmitted to the eNodeB 210. Atthe eNodeB 210, the uplink signals from the UE 250 may be received bythe eNodeB antennas 234, processed by the eNodeB modulators/demodulators232, detected by a eNodeB MIMO detector 236 if applicable, and furtherprocessed by a eNodeB reception processor 238 to obtain decoded data andcontrol information sent by the UE 250. The eNodeB reception processor238 may provide the decoded data to a eNodeB data sink 246 and thedecoded control information to the eNodeB controller/processor 240.

The eNodeB controller/processor 240 and the UE controller/processor 280may direct the operation at the eNodeB 210 and the UE 250, respectively.The UE controller/processor 280 and/or other processors and modules atthe UE 250 may also perform or direct, e.g., the execution of thefunctional blocks illustrated in FIG. 6 and/or FIG. 10, and/or otherprocesses for the techniques described herein (e.g., flowchartsillustrated in FIGS. 8, 9, 11, 12, etc.). In some aspects, at least aportion of the execution of these functional blocks and/or processes maybe performed by block 281 in the UE controller/processor 280. The eNodeBmemory 242 and the UE memory 282 may store data and program codes forthe eNodeB 210 and the UE 250, respectively. For example, the UE memory282 may store configuration information for multiple connectivityprovided by the eNodeB 210 and/or another eNodeB. A scheduler 244 may beused to schedule UE 250 for data transmission on the downlink and/oruplink.

In one configuration, the UE 250 may include means for establishing afirst connection served by at least a first cell. The UE 250 may alsoinclude means for establishing a second connection served by at least asecond cell to facilitate communicating with at least the first cell andat least the second cell. The UE 250 may further include means fordetermining a timing difference between at least the first cell and atleast the second cell. The UE 250 can also include means for reportingthe timing difference to at least the first cell over the firstconnection or to at least the second cell over the second connection. Inanother configuration, the UE 250 can additionally or alternativelyincludes means for receiving a configuration message to establish asecond connection served by at least a second cell, means for estimatinga timing difference between at least the first cell and at least thesecond cell, means for reporting the timing difference to at least thefirst cell over the first connection, and means for configuring thesecond connection served by at least the second cell based at least inpart on reporting the timing difference to at least the first cell. Inone aspect, the aforementioned means may be the UE controller/processor280, the UE memory 282, the UE reception processor 258, the UE MIMOdetector 256, the UE modulators/demodulators 254, and the UE antennas252 configured to perform the functions recited by the aforementionedmeans. In another aspect, the aforementioned means may be a module,component, or any apparatus configured to perform the functions recitedby the aforementioned means. Examples of such modules, components, orapparatus may be described with respect to FIG. 6 and/or FIG. 10.

FIG. 3 is a block diagram conceptually illustrating an aggregation ofcarriers and/or connections at a UE, in accordance with an aspect of thepresent disclosure. The aggregation may occur in a system 300 includinga multi-mode UE 315, which can communicate with an eNodeB 305-a usingone or more component carriers 1 through N (CC₁-CC_(N)), and/or with asecondary eNodeB 305-b using one or more component carriers M through P(CC_(M)-CC_(P)). For example, the eNodeB 305-a and/or secondary eNodeB305-b may include an AP, femto cell, pico cell, etc. UE 315 can includea communicating component 640 for determining and/or reporting timingdifferences among various eNodeBs 305-a, 305-b serving the UE 315 inmultiple connectivity. The eNodeBs 305-a and/or 305-b can include acommunicating component 1040 for receiving reported timing differencesfrom the UE 315 with other eNodeBs for determining scheduling of one ormore operations for the UE 315. UE 315 may be a multi-mode UE in thisexample that supports more than one radio access technology (RAT). Forexample, the UE 315 may support at least a WWAN radio access technology(e.g., LTE) and/or a WLAN radio access technology (e.g., Wi-Fi). Amulti-mode UE may also support carrier aggregation and/or multipleconnectivity carrier aggregation as described herein. The UE 315 may bean example of one of the UEs of FIG. 1, FIG. 2, FIG. 4, FIG. 5, FIG. 6,FIG. 10. The eNodeB 305-a and/or secondary eNodeB 305-b may be anexample of one of the eNodeBs, base stations, network entities, etc. ofFIG. 1, FIG. 2, FIG. 4, FIG. 5, FIG. 6, FIG. 10. While only one UE 315,one eNodeB 305-a, and one secondary eNodeB 305-b are illustrated in FIG.3, it will be appreciated that the system 300 can include any number ofUEs 315, eNodeBs 305-a, and/or secondary eNodeBs 305-b. In one specificexample, UE 315 can communicate with one eNodeB 305-a over one or moreLTE component carriers 330-1 to 330-N while communicating with anothereNodeB 305-b over another one or more LTE component carriers 330-M to330-P.

The eNodeB 305-a can transmit information to the UE 315 over forward(downlink) channels 332-1 through 332-N on LTE component carriers CC₁through CC_(N) 330. In addition, the UE 315 can transmit information tothe eNodeB 305-a over reverse (uplink) channels 334-1 through 334-N onLTE component carriers CC₁ through CC_(N). Similarly, the eNodeB 305-bmay transmit information to the UE 315 over forward (downlink) channels332-m through 332-p on LTE component carriers CC_(M) through CC_(P) 330.In addition, the UE 315 may transmit information to the eNodeB 305-bover reverse (uplink) channels 334-m through 334-p on LTE componentcarriers CC_(M) through CC_(P) 330.

In describing the various entities of FIG. 3, as well as other figuresassociated with some of the disclosed embodiments, for the purposes ofexplanation, the nomenclature associated with a 3GPP LTE or LTE-Awireless network is used. However, it is to be appreciated that thesystem 300 can operate in other networks such as, but not limited to, anOFDMA wireless network, a CDMA network, a 3GPP2 CDMA2000 network and thelike.

In multi-carrier operations, the downlink control information (DCI)messages associated with different UEs 315 can be carried on multiplecomponent carriers. For example, the DCI on a PDCCH can be included onthe same component carrier that is configured to be used by a UE 315 forphysical downlink shared channel (PDSCH) transmissions (i.e.,same-carrier signaling). Alternatively, or additionally, the DCI may becarried on a component carrier different from the target componentcarrier used for PDSCH transmissions (i.e., cross-carrier signaling). Insome implementations, a carrier indicator field (CIF), which may besemi-statically enabled, may be included in some or all DCI formats tofacilitate the transmission of PDCCH control signaling from a carrierother than the target carrier for PDSCH transmissions (cross-carriersignaling).

In the present example, the UE 315 may receive data from one eNodeB305-a. However, users on a cell edge may experience high inter-cellinterference which may limit the data rates. Multiflow allows UEs toreceive data from two eNodeBs 305-a and 305-b concurrently. In someaspects, the two eNodeBs 305-a may be non-collocated and may beconfigured to support multiple connectivity carrier aggregation.Multiflow works by sending and receiving data from the two eNodeBs305-a/305-b in two totally separate streams when a UE is in range of twocell towers in two adjacent cells at the same time (see FIG. 5 below).The UE talks to two eNodeB 305-a/305-b simultaneously when the device ison the edge of either eNodeBs' reach. By scheduling two independent datastreams to the mobile device from two different eNodeBs at the sametime, multiflow exploits uneven loading in the wireless communicationnetworks. This helps improve the cell edge user experience whileincreasing network capacity. In one example, throughput data speeds forusers at a cell edge may double. In some aspects, multiflow may alsorefer to the ability of a UE to talk to a WWAN tower (e.g., cellulartower) and a WLAN tower (e.g., AP) simultaneously when the UE is withinthe reach of both towers. In such cases, the towers may be configured tosupport carrier aggregation through multiple connections when the towersare not collocated. FIG. 4 is a block diagram conceptually illustratingan example of data paths 445 and 450 between a UE 415 and a PDN 440(e.g., Internet or one or more components to access the Internet) inaccordance with an aspect of the present disclosure. The data paths 445,450 are shown within the context of a wireless communications system 400for aggregating data from different eNodeBs 405-a and 405-b, which mayor may not use the same RAT. The system 200 of FIG. 2 may be an exampleof portions of the wireless communications system 400. The wirelesscommunications system 400 may include a multi-mode UE 415, an eNodeB405, a secondary eNodeB 405-b that can be coupled to the eNodeB 405-avia a backhaul link 438 (e.g., based on a X2 interface), an evolvedpacket core (EPC) 480, a PDN 440, and a peer entity 455. UE 415 caninclude a communicating component 640 for determining and/or reportingtiming differences among various eNodeBs 405-a, 405-b serving the UE 415in multiple connectivity. The eNodeBs 405-a and/or 405-b can include acommunicating component 1040 for receiving reported timing differencesfrom the UE 415 with other eNodeBs for determining scheduling of one ormore operations for the UE 415. The multi-mode UE 415 may be configuredto support carrier aggregation, multiple connectivity (e.g., dualconnectivity) carrier aggregation, and/or the like. The EPC 480 mayinclude a mobility management entity (MME) 430, a serving gateway (SGW)432, and a PDN gateway (PGW) 434. A home subscriber system (HSS) 435 maybe communicatively coupled with the MME 430. The UE 415 may include anLTE radio 420 and an LTE radio 425. These elements may represent aspectsof one or more of their counterparts described above with reference tothe previous or subsequent Figures. For example, the UE 415 may be anexample of UEs in FIG. 1, FIG. 2, FIG. 3, FIG. 5, FIG. 6, FIG. 10, theeNodeB 405-a may be an example of the eNodeBs/base stations/networkentities of FIG. 1, FIG. 2, FIG. 3, FIG. 5, FIG. 6, FIG. 10, thesecondary eNodeB 405-b may be an example of the secondary eNodeB/basestations/network entities of FIG. 1, FIG. 2, FIG. 3, FIG. 5, FIG. 6,FIG. 10, and/or the EPC 480 may be an example of the core network 130 ofFIG. 1. The eNodeBs 405-a and 405-b in FIG. 4 may be not be collocatedor otherwise may not be in high-speed communication with each other. Inaddition, in an example, eNodeBs 405 and 405-b may communicate withdifferent EPCs 480.

Referring back to FIG. 4, the eNodeB 405-a and/or 405-b may be capableof providing the UE 415 with access to the PDN 440 using the aggregationof one or more LTE component carriers (e.g., with one or more eNodeBs).Accordingly, the UE 415 may involve carrier aggregation in dualconnectivity, where one connection is to one network entity (eNodeB405-a) and the other connection is to a different network entity (eNodeB405-b). It is to be appreciated that UE 415 can communicate withadditional eNodeBs 405-a and/or 405-b via additional data paths 445, 450that traverse the EPC 408 or not to access PDN 440 to provide multipleconnectivity wireless communications with multiple eNodeBs, carrieraggregation with multiple cells of an eNodeB, etc. Using this access tothe PDN 440, the UE 415 may communicate with the peer entity 455. TheeNodeB 405-a and/or 405-b may provide access to the PDN 440 through theEPC 480 (e.g., through data path 445 and/or 450). In the depictedexample, the UE 415 can communicate with eNodeB 405 as a MeNodeB and theeNodeB 405-b as SeNodeB over eNodeB-specific bearers. In an example,eNodeBs 405-a and 405-b can communicate with one another over an X2connection 438 to aggregate UE 415 communications for providing the EPC480. In this example, UE 415 can access the PDN 440 by using the bearerwith eNodeB 405 and/or secondary eNodeB 405-b (or related cells or cellgroups), which can map communications over the data paths 445 and 450 toaccess the PDN 440.

The MME 430 may be the control node that processes the signaling betweenthe UE 415 and the EPC 480. The MME 430 may provide bearer andconnection management. The MME 430 may, therefore, be responsible foridle mode UE tracking and paging, bearer activation and deactivation,and SGW selection for the UE 415. The MME 430 may communicate with theeNodeBs 405-a and/or 405-b over an S1-MME interface. The MME 430 mayadditionally authenticate the UE 415 and implement Non-Access Stratum(NAS) signaling with the UE 415.

The HSS 435 may, among other functions, store subscriber data, manageroaming restrictions, manage accessible access point names (APNs) for asubscriber, and associate subscribers with MMEs 430. The HSS 435 maycommunicate with the MME 430 over an S6a interface defined by theEvolved Packet System (EPS) architecture standardized by the 3GPPorganization.

All user IP packets transmitted over LTE may be transferred througheNodeBs 405-a and/or 405-b to the SGW 432, which may be connected to thePDN gateway 434 over an S5 signaling interface and the MME 430 over anS11 signaling interface. The SGW 432 may reside in the user plane andact as a mobility anchor for inter-eNodeB handovers and handoversbetween different access technologies. The PDN gateway 434 may provideUE IP address allocation as well as other functions.

The PDN gateway 434 may provide connectivity to one or more externalpacket data networks, such as PDN 440, over an SGi signaling interface.The PDN 440 may include the Internet, an Intranet, an IP MultimediaSubsystem (IMS), a Packet-Switched (PS) Streaming Service (PSS), and/orother types of PDNs.

In the present example, user plane data between the UE 415 and the EPC480 may traverse the same set of one or more EPS bearers, irrespectiveof whether the traffic flows over data path 445 of the LTE link or datapath 450. Signaling or control plane data related to the set of one ormore EPS bearers may be transmitted between the LTE radio 420 of the UE415 and the MME 430 of the EPC 480, by way of the eNodeBs 405-a and/or405-b.

While aspects of FIG. 4 have been described with respect to LTE, similaraspects regarding aggregation and/or multiple connections may also beimplemented with respect to UMTS or other similar system or networkwireless communications radio technologies.

FIG. 5 is a diagram conceptually illustrating multiple connectivitycarrier aggregation, in accordance with an aspect of the presentdisclosure. A wireless communications system 500 may include a mastereNodeB 505-a (MeNodeB or MeNB) having a set or group of cells referredto as a master cell group or MCG (or PCG) that may be configured toserve the UE 515. The MCG may include one primary cell (PCell_(MCG))510-a and one or more secondary cells 510-b (only one is shown). Thewireless communications system 500 may also include a secondary eNodeB505-b (SeNodeB or SeNB) having a set or group of cells referred to as asecondary cell group or SCG that may be configured to serve the UE 515.The SCG may include one primary cell (PCell_(SCG)) 512-a and one or moresecondary cells 512-b (only one is shown). Also shown is a UE 515 thatsupports carrier aggregation for multiple connectivity (e.g., dualconnectivity). The UE 515 may communicate with the MeNodeB 505-a, or arelated PCell_(MCG), via communication link 525-a and with the SeNodeB505-b. or a related PCell_(SCG), via communication link 525-b. UE 515can include a communicating component 640 for determining and/orreporting timing differences among various eNodeBs 505-a, 505-b servingthe UE 515 in multiple connectivity. The eNodeBs 505-a and/or 505-b caninclude a communicating component 1040 for receiving reported timingdifferences from the UE 515 with other eNodeBs for determiningscheduling of one or more operations for the UE 515.

In an example, the UE 515 may aggregate component carriers from the sameeNodeB or may aggregate component carriers from collocated ornon-collocated eNodeBs. In such an example, the various cells (e.g.,different component carriers (CCs)) being used can be easily coordinatedbecause they are either handled by the same eNodeB or by eNodeBs thatcan communicate control information. When the UE 515, as in the exampleof FIG. 5, performs carrier aggregation when in communication with twoeNodeBs that are non-collocated, then the carrier aggregation operationmay be different due to various network conditions. In this case,establishing a primary cell (PCell_(SCG)) in the secondary eNodeB 505-bmay allow for appropriate configurations and controls to take place atthe UE 515 even though the secondary eNodeB 505-b is non-collocated withthe primary eNodeB 505-a.

In the example of FIG. 5, the carrier aggregation may involve certainfunctionalities by the PCell_(MCG) of the MeNodeB 505-a. For example,the PCell_(MCG) may handle certain functionalities such as physicaluplink control channel (PUCCH), contention-based random access controlchannel (RACH), and semi-persistent scheduling to name a few. Carrieraggregation with dual or multiple connectivity to non-collocated eNodeBsmay involve having to make some enhancements and/or modifications to themanner in which carrier aggregation is otherwise performed. Some of theenhancements and/or modifications may involve having the UE 515connected to the MeNodeB 505-a and to the SeNodeB 505-b as describedabove. Other features may include, for example, having a timeradjustment group (TAG) comprise cells of one of the eNodeBs, havingcontention-based and contention-free random access (RA) allowed on theSeNodeB 505-b, separate discontinuous reception (DRX) procedures for theMeNodeB 505-a and to the SeNodeB 505-b, having the UE 515 send a bufferstatus report (BSR) to the eNodeB where the one or more bearers (e.g.,eNodeB specific or split bearers) are served, as well as enabling one ormore of power headroom report (PHR), power control, semi-persistentscheduling (SPS), and logical channel prioritization in connection withthe PCell_(SCG) in the secondary eNodeB 505-b. The enhancements and/ormodifications described above, and well as others provided in thedisclosure, are intended for purposes of illustration and not oflimitation.

For carrier aggregation in dual connectivity, different functionalitiesmay be divided between the MeNodeB 505-a and the SeNodeB 505-b. Forexample, different functionalities may be statically divided between theMeNodeB 505-a and the SeNodeB 505-b or dynamically divided between theMeNodeB 505-a and the SeNodeB 505-b based on one or more networkparameters. In an example, the MeNodeB 505-a may perform upper layer(e.g., above the media access control (MAC) layer) functionality via aPCell_(MCG), such as but not limited to functionality with respect toinitial configuration, security, system information, and/or radio linkfailure (RLF). As described in the example of FIG. 5, the PCell_(MCG)may be configured as one of the cells of the MeNodeB 505-a that belongto the MCG. The PCell_(MCG) may be configured to provide lower layerfunctionalities (e.g., MAC/PHY layer) within the MCG.

In an example, the SeNodeB 505-b may provide configuration informationof lower layer functionalities (e.g., MAC/PHY layers) for the SCG. Theconfiguration information may be provided by the PCell_(SCG) as one ormore radio resource control (RRC) messages, for example. The PCell_(SCG)may be configured to have the lowest cell index (e.g., identifier or ID)among the cells in the SCG. For example, some of the functionalitiesperformed by the SeNodeB 505-b via the PCell_(SCG) may include carryingthe PUCCH, configuring the cells in the SCG to follow the DRXconfiguration of the PCell_(SCG), configure resources forcontention-based and contention-free random access on the SeNodeB 505-b,carrying downlink (DL) grants having transmit power control (TPC)commands for PUCCH, estimating path loss based on PCell_(SCG) for othercells in the SCG, providing common search space for the SCG, andproviding SPS configuration information for the UE 515.

In some aspects, the PCell_(MCG) may be configured to provide upperlevel functionalities to the UE 515 such as security, connection to anetwork, initial connection, and/or radio link failure, for example. ThePCell_(MCG) may be configured to carry physical uplink control channel(PUCCH) for cells in the MCG, to include the lowest cell index among theMCG, to enable the MCG cells to have the same discontinuous reception(DRX) configuration, to configure random access resources for one orboth of contention-based and contention-free random access on theMeNodeB 505-a, to enable downlink grants to convey transmit powercontrol (TPC) commands for PUCCH, to enable path loss estimation forcells in the MCG, to configure common search space for the MeNodeB505-a, and/or to configure semi-persistent scheduling.

In some aspects, the PCell_(SCG) may be configured to carry PUCCH forcells in the SCG, to include the lowest cell index among the SCG, toenable the SCG cells to have the same DRX configuration, to configurerandom access resources for one or both of contention-based andcontention-free random access on the SeNodeB 505-b, to enable downlinkgrants to convey TPC commands for PUCCH, to enable path loss estimationfor cells in the SCG, to configure common search space for the SeNodeB505-b, and/or to configure semi-persistent scheduling.

Returning to the example of FIG. 5, the UE 515 may support parallelPUCCH and physical uplink shared channel (PUSCH) configurations for theMeNodeB 505-a and the SeNodeB 505-b. In some cases, the UE 515 may use aconfiguration (e.g., UE 515 based) that may be applicable to bothcarrier groups. These PUCCH/PUSCH configurations may be provided throughRRC messages, for example.

The UE 515 may also support parallel configuration for simultaneoustransmission of acknowledgement (ACK)/negative acknowledgement (NACK)and channel quality indicator (CQI) and for ACK/NACK/sounding referencesignal (SRS) for the MeNodeB 505-a and the SeNodeB 505-b. In some cases,the UE 515 may use a configuration (e.g., UE based and/or MCG or SCGbased) that may be applicable to both carrier groups. Theseconfigurations may be provided through RRC messages, for example.

FIG. 6 is a block diagram 600 conceptually illustrating an example of aUE 615 and components configured in accordance with an aspect of thepresent disclosure. FIGS. 8 and 9, which are described in conjunctionwith FIG. 6 herein, illustrate example methods 800 and 900 in accordancewith aspects of the present disclosure. Although the operationsdescribed below in FIGS. 8 and 9 are presented in a particular orderand/or as being performed by an example component, it should beunderstood that the ordering of the actions and the componentsperforming the actions may be varied, depending on the implementation.Moreover, it should be understood that the following actions orfunctions may be performed by a specially-programmed processor, aprocessor executing specially-programmed software or computer-readablemedia, or by any other combination of a hardware component and/or asoftware component capable of performing the described actions orfunctions.

Referring to FIG. 6, a eNodeB 605-a (MeNodeB of a PCell_(MCG)), a eNodeB605-b (SeNodeB of a PCell_(SCG)), and the UE 615 of diagram 600 may beone of the base stations/eNodeBs (or APs) and UEs as described invarious Figures. The MeNodeB 605-a, or a PCell_(MCG) related thereto,and the UE 615 may communicate over communication link 625-a. TheSeNodeB 605-b, or a PCell_(SCG) related thereto, and the UE 615 maycommunicate over communication link 625-b. UE 615 may be configured todetermine a report a timing difference between the cells configured bythe MeNodeB 605-a and SeNodeB 605-b (e.g., over communication links625-a and 625-b) to facilitate performing operations that may benefitfrom timing alignment of the cells configured by the MeNodeB 605-aand/or SeNodeB 605-b. MeNodeB 605-a and SeNodeB 605-b may communicateover a backhaul link 634 to facilitate aggregating carriers of the UE615 in multiple connectivity wireless communications, as described. Inaddition, in aspects described herein, MeNodeB 605-a and SeNodeB 605-bmay communicate reported timing difference information over the backhaullink 634 to facilitate scheduling the UE 615 for one or more operationsfor which synchronizing timing may be beneficial (e.g., configuringmeasurement gaps, DRX-on durations, etc.).

In this regard, UE 615 may include a communicating component 640 fordetermining and/or reporting a timing difference between communicationlinks 625-a and 625-b with eNodeBs 605-a and 605-b. Communicatingcomponent 640 can include, or can be in communication with, a timingdifference determining component 650 for determining a timing differencebetween the cells or cell groups that serve communication links 625-aand 625-b, a timing difference reporting component 652 for reporting thetiming difference between the cells to one or more eNodeBs or othernetwork entities, and a timing difference triggering component 654 fordetecting one or more events that can cause determining and reportingtiming difference. Communicating component 640 can optionally include,or be in communication with, a connection configuring component 656 forsuspending or resuming configuration of one or more operations based onwhether the timing difference is reported, an acknowledgement ofreceiving the difference is received, etc.

FIG. 7 depicts example timing differences 700, 702, and 704 betweencells configured by an MeNodeB and SeNodeB, and respective measurementgap determinations, in accordance with various aspects of the presentdisclosure. At timing difference 700, timing difference determiningcomponent 650 determines a timing difference between the MeNodeB 605-aand SeNodeB 605-b where the subframe boundaries are substantiallyaligned, but SFNs at a given time are different and/or position of thesubframes within the system frame at a given time are different. In thisexample, timing difference reporting component 652 can report a timingdifference between the MeNodeB 605-a and SeNodeB 605-b with highaccuracy, and the timing difference can be considered based on thesubframe alignment. In this example, subframes for measurement gaps canbe selected for the cell configured by the SeNodeB 605-b and UE 615 assubstantially aligned to the subframes selected for the cell configuredby the MeNodeB 605-a and UE 615. In the depicted example, subframes 2-7of SFN 0 (e.g., substantially aligned with subframes 7-9 of SFN 99 andsubframes 0-2 of SFN 100) used by the cell provided by MeNodeB 605-a areselected as a measurement gap to allow UE 615 to measure cells ofanother RAT and/or frequency. In this regard, SeNodeB 605-b can schedulean aligned measurement gap based on measurement gaps defined for theMeNodeB 605-a and the reported timing difference (e.g., measurement gapsubframe number at the MeNodeB 605-a plus at least a number of subframesindicated by or otherwise determined from the timing offset). In thisexample, the aligned measurement gap can be scheduled by SeNodeB 605-bto use the same number of subframes as the measurement gap scheduled bythe MeNodeB 605-a since the subframes are aligned, and thus possibleinaccuracies in determining the timing difference need not beconsidered. Moreover, though shown and described as applying tomeasurement gap, it is to be appreciated that subframes 2-7 of SFN 0 (ora less or greater number of subframes that may or may not span multipleSFNs) can be aligned by the SeNodeB 605-b, based on the subframes forthe operation scheduled at MeNodeB 605-a and the reported timingdifference, for additional operations, such as DRX on durations, and/orthe like. This aligning of the measurement gap is referred to herein as“example 1.”

In other examples, timing differences reported by the UE 615 may not beexpected to have such high accuracy, and the timing differences of theMeNodeB 605-a and SeNodeB 605-b may be such that subframe boundaries arenot aligned. At time difference 702, the subframe boundary offsetbetween the timings of MeNodeB 605-a and SeNodeB 605-b may be outside ofthe possible timing estimate inaccuracy of the UE 615, denoted δ (e.g.,δ<subframe boundary offset<subframe_length−δ). For example, the subframeboundary offset may be determined as the timing offset modulo thesubframe_length (e.g., 1 ms in LTE). In this example, it can bedetermined which of MeNodeB 605-a and SeNodeB 605-b is ahead of theother in subframe timing based at least in part on whether the timingdifference is >0.5*subframe_length (or some other threshold) or not.Thus, in this example, subframes can be aligned in the MeNodeB 605-a andSeNodeB 605-b such that subframes of the SeNodeB 605-b can be selectedfor the UE 615 which are substantially aligned to the subframes of theMeNodeB 605-a selected for the UE 615 for certain operations and alsoincluding an additional subframe before or after the aligned subframes.Determining whether to include the subframe before or after is based atleast in part on determining whether SeNodeB timing is ahead of orbehind the MeNodeB timing. In the depicted example, subframes 2-7 of SFN0 at the MeNodeB 605-a are selected as a measurement gap to allow UE 615to measure cells of another RAT and/or frequency. In this regard,SeNodeB 605-b can schedule subframes for an aligned measurement gap forthe UE 615 based on the measurement gap defined by the MeNodeB 605-a andthe reported timing difference. In this example, the aligned measurementgap can be scheduled by SeNodeB 605-b to use the same number ofsubframes as the measurement gap scheduled by the MeNodeB 605-a plusanother subframe to account for timing inaccuracy, where the additionalsubframe is scheduled before the number of subframes (based ondetermining the SeNodeB 605-b to be ahead of the MeNodeB 605-a insubframe timing). Moreover, though shown and described as applying tomeasurement gap, it is to be appreciated that subframes 2-7 of SFN 0 (ora less or greater number of subframes that may or may not span multipleSFNs) can be aligned by the SeNodeB 605-b based, on the subframes forthe operation scheduled at MeNodeB 605-a and the reported timingdifference (and including the additional subframe before or after), foradditional operations, such as DRX on durations, and/or the like. Thisaligning of the measurement gap is referred to herein as “example 2.”

At time difference 704, the subframe boundary offset may be inside ofthe possible timing estimate inaccuracy (e.g., δ>=subframe boundaryoffset or subframe boundary offset>=subframe_length−δ). In this example,it may not be determined which of MeNodeB 605-a and SeNodeB 605-b isahead of the other in subframe timing. Thus, in this example, subframescan be aligned in the MeNodeB 605-a and SeNodeB 605-b such thatsubframes can be selected at the SeNodeB 605-b for the UE 615 which aresubstantially aligned to the subframes selected for the MeNodeB 605-a toprovide certain operations to the UE 615 and also including anadditional subframe before and an additional subframe after the alignedsubframes. In the depicted example, subframes 1-6 of SFN 0 at theMeNodeB 605-a are selected as a measurement gap to allow UE 615 tomeasure cells of another RAT and/or frequency. In this regard, analigned measurement gap at the SeNodeB 605-b for the UE 615 can bedetermined based on measurement gap defined for the MeNodeB 605-a andthe reported timing difference, and the SeNodeB 605-b can accordinglyschedule the measurement gap for the UE 615 in the aligned measurementgap with an additional subframe scheduled before the aligned measurementgap and an additional subframe scheduled after the aligned measurementgap. Moreover, though shown and described as applying to measurementgap, it is to be appreciated that subframes 1-6 of SFN 0 (or a less orgreater number of subframes that may or may not span multiple SFNs) canbe aligned by the SeNodeB 605-b based, on the subframes for theoperation scheduled at MeNodeB 605-a and the reported timing difference(and including the additional subframes before and after), foradditional operations, such as DRX on durations, and/or the like. Thisaligning of the measurement gap is referred to herein as “example 3.”

FIG. 8 illustrates an example method 800 for reporting timing differencebetween one or more cells or cell groups to one or more eNodeBs. Method800 includes, at Block 810, establishing a first connection served by atleast a first cell. Communicating component 640 (FIG. 6) can establishthe first connection served by at least the first cell, which caninclude communication link 625-a with MeNodeB 605-a or a related cell orcell group (e.g., MCG) thereof. For example, this can includecommunicating component 640 performing one or more procedures to connectwith the MeNodeB 605-a and/or one or more related cells thereof or in arelated group of cells (e.g., performing a random access procedure withone or more cells). Method 800 also includes, at Block 812, establishinga second connection served by at least a second cell. Communicatingcomponent 640 can also establish the second connection served by atleast the second cell, which can include communication link 625-b withSeNodeB 605-b or a related cell or cell group (e.g., SCG) thereof. Forexample, this can include communicating component 640 performing one ormore procedures to connect with the SeNodeB 605-b and/or one or morerelated cells thereof or in a related group of cells (e.g., performing arandom access procedure with one or more cells). As describedpreviously, the connections can be configured using multipleconnectivity to provide the UE 615 with communications concurrentlyconfigured in an MCG and SCG. MeNodeB 605-a and SeNodeB 605-b, however,may use different timings such that communication links 625-a and 625-bmay use different subframe numbers for subframes configured in similarperiods of time and/or such that the subframe boundaries of thecommunication links 625-a and 625-b are not aligned in time.

Method 800 includes, at Block 814, receiving a reporting configurationspecifying one or more parameters related to reporting a timingdifference between cells or cell groups. Timing difference triggeringcomponent 654 can receive the reporting configuration specifying the oneor more parameters related to reporting the timing difference betweencells or cell groups. For example, timing difference triggeringcomponent 654 can receive the reporting configuration from the first orsecond cell (e.g., the MeNodeB 605-a, SeNodeB 605-b, related cells orcell groups, etc.), from a stored or retrieved configuration at the UE615, in a configuration received from other network entities (e.g., uponinitiating connection in a wireless network), etc. For example, the oneor more parameters in the reporting configuration can specify a type oftrigger for the UE 615 to utilize in determining and/or reporting atiming difference between cells or cell groups, one or more parametersrelated to detecting a condition for determining and/or reporting thetiming difference (e.g., one or more thresholds as described herein),etc. In this regard, for example, timing difference triggering component654 may monitor the one or more parameters to detect the trigger orcondition for determining the timing difference between the cells orcell groups and/or determining whether to report the determined timingdifference.

For example, the trigger can relate to a periodic time trigger fordetecting the condition for determining and reporting the timingdifference after expiration of a period of time. Thus, for example,timing difference triggering component 654 may determine to initializeand maintain a timer, and/or may determine timer-related information(e.g., timer value), based on the one or more parameters in thereporting configuration, for determining and/or reporting the timingdifference. In this example, timing difference triggering component 654can initialize the timer after reporting a previous timing difference toMeNodeB 605-a and/or SeNodeB 605-b. For example, when the timer expires,timing difference determining component 650 can determine the timingdifference and/or timing difference reporting component 652 can reportthe timing difference to MeNodeB 605- and/or SeNodeB 605-b, as describedfurther herein. In an example, timing difference reporting component 652can report the timing difference subject to additional conditionsdescribed herein or otherwise. Timing difference triggering component654 may then restart the timer based on a timer value received in theconfiguration, etc. for determining a next period during which to reportor at least determine the timing difference between the MCG and SCG (orrelated eNodeBs, cells, etc.).

In another example, the one or more parameters in the reportingconfiguration can relate to a trigger for comparing a determined timingdifference between the cells or cell groups to a timing differenceconfigured by or otherwise assumed by the network (e.g., by one or moreof the cells or cell groups). In this example, timing differencereporting component 652 can report the timing difference to the MeNodeB605-a, SeNodeB 605-b. etc. when the comparison between the timingdifferences results in a difference that achieves a threshold. Forexample, timing difference triggering component 654 may determine theassumed timing difference configured by the network and/or the thresholdfrom the one or more parameters of the reporting configuration, from oneor more parameters otherwise configured by a network at the UE 615, froma stored configuration at the UE 615, and/or the like. Thus, forexample, timing difference determining component 650 may determine thetiming difference between the first cell and second cell periodically(e.g., based on a periodic timer defined by timing difference triggeringcomponent 654, which may be based on the one or more parameters in thereporting configuration, as described above), and timing differencereporting component 652 may report the timing difference where thetiming difference differs from the assumed timing difference by at leastthe threshold.

In another example, the one or more parameters in the reportingconfiguration can relate to a trigger for similarly comparing thedetermined timing difference between the first cell and second cell (orrelated cell groups) to a previously determined and/or reported timingdifference of the first cell and second cell (or related cell groups),as determined by timing difference determining component 650 and/or asreported by timing difference reporting component 652. In this example,where the determined timing difference and the previously determinedtiming difference between the first cell and second cell (or relatedcell groups) differ by more than a threshold, timing differencereporting component 652 can report the timing difference to the MeNodeB605-a, SeNodeB 605-b. etc. as described herein. For example, thethreshold may be included in the one or more parameters of the reportingconfiguration received by timing difference triggering component 654.

In another example, the one or more parameters in the reportingconfiguration can relate to a trigger for determining a change in thenumber of subframes impacted by the timing difference change. Forexample, timing difference triggering component 654 can determinewhether a timing difference between the first cell and second cell (orrelated cell groups) determined by timing difference determiningcomponent 650 impacts a larger number of subframes than a previouslydetermined timing difference between the first cell and second cell (orrelated cell groups). As described, for example, the timing differencemeasured between the cells by timing difference determining component650 may have some degree of inaccuracy and/or detecting a timingdifference between the cells or cell groups may indicate somemisalignment of subframe boundaries over communication links 625-a and625-b. Thus, timing difference triggering component 654 can determinewhether the detected timing difference within subframe boundaries (e.g.,timing difference modulo the subframe_length) has moved from outside ofa range corresponding to the inaccuracy δ (e.g.,δ<offset<subframe_length−δ) in a previous time difference determinationto inside the range corresponding to the inaccuracy δ (e.g., δ>=offsetor offset>=subframe_length−δ) in the current time differencedetermination, and/or vice versa. Where the detected timing differencewithin the subframe boundaries has moved, timing difference reportingcomponent 652 may determine to report the timing difference to MeNodeB605-a, SeNodeB 605-b, etc., as described herein. It is to be appreciatedthat, timing difference determining component 650 can determine thepossible timing inaccuracy δ for the UE 615 based on a configurationstored by the UE 615 or otherwise received by one or more networkentities as one or more parameters in the reporting configuration oranother configuration, etc.

In another example, the one or more parameters in the reportingconfiguration can relate to a prohibit timer, which can be initializedand managed by timing difference triggering component 654. Timingdifference triggering component 654 can initialize the prohibit timerbased on a timer value configured by the network (e.g., indicated in theone or more parameters in the reporting configuration, indicated inanother configuration by MeNodeB 605-a, SeNodeB 605-b, or other networkentities, etc.). Moreover, for example, timing difference triggeringcomponent 654 can initialize the prohibit timer after reporting aprevious timing difference. Thereafter, timing difference determiningcomponent 650 can refrain from determining a timing difference, and/ortiming difference reporting component 652 can refrain from reporting thetiming difference, at least until after expiration of the prohibit timeris determined. After the prohibit timer expires, timing differencedetermining component 650 can determine a timing difference between thefirst cell and second cell, and/or timing difference reporting component652 can report the timing difference. For example, determining thetiming difference and/or reporting the timing difference may beadditionally based on one or more of the other described triggers.

In another example, the one or more parameters in the reportingconfiguration can relate to a request received from the network todetect and report the timing (e.g., a request from MeNodeB 605-a,SeNodeB 605-b, or other network entities via one or more of the MeNodeB605-a or SeNodeB-605-b).

Method 800 also includes, at Block 816, determining a timing differencebetween at least the first cell and at least the second cell. Timingdifference determining component 650 can determine the timing differencebetween the first cell (e.g., a cell or cell group provided at leastpartially by MeNodeB 605-a) and the second cell (e.g., a cell or cellgroup provided at least partially by SeNodeB 605-b). As described,timing difference determining component 650 may determine the timingdifference based on one or more of the parameters in the reportingconfiguration described above or otherwise (e.g., based on a definedperiodicity). In addition, for example, timing difference determiningcomponent 650 can determine the timing difference based on one or moreparameters received over respective communication links 625-a and 625-b(e.g., system information received from the MeNodB 605-a and/or SeNodeB605-b). The timing difference may include a number of milliseconds,microseconds, or other measure of time between subframes or subframeboundaries of communication link 625-a and communication link 625-b, anumber of subframes between a subframe number of communication link625-a and a subframe number of communication link 625-b occurring in thesame or overlapping time period, an indication of a SFN, subframenumber, etc. and an associated actual time for the start of the SFN,subframe number etc. for both the MeNodeB 605-a and SeNodeB 605-b (orrelated cells or cell groups), and/or the like. As described, forexample, timing difference determining component 650 can determine thesubframe numbers for the cells in one or more time periods based onsystem information received from the respective MeNodeB 605-a andSeNodeB 605-b (e.g., in one or more MIBs).

Method 800 further includes, at Block 818, reporting the timingdifference to at least the first cell over the first connection or to atleast the second cell over the second connection based at least in parton the reporting configuration. Timing difference reporting component652 can report the timing difference to at least the first cell (e.g., acell or cell group of MeNodeB 605-a) over a first connection (e.g.,communication link 625-a) or to at least the second cell (e.g., a cellor cell group of SeNodeB 605-b) over the second connection (e.g.,communication link 625-b) based on the reporting configuration (e.g., asreceived by timing difference triggering component 654). In one example,timing difference reporting component 652 can report the timingdifference based at least in part on the periodic time trigger describedabove such that the timing difference triggering component 654 caninitialize the timer after each reporting of the timing difference, andtiming difference reporting component 652 can report the timingdifference based on expiration of the timer. In another example, asdescribed, timing difference reporting component 652 can report thetiming difference based at least in part on detecting that the timingdifference differs from a timing difference indicated by the network(e.g., by MeNodeB 605-a or other network entity in the one or moreparameters of the reporting configuration or other configuration) by atleast a threshold. In yet another example, as described, timingdifference reporting component 652 can report the timing differencebased at least in part on detecting that the timing difference differsfrom a timing difference previously reported by timing differencereporting component 652 at least by a threshold. In a further example,as described, timing difference reporting component 652 can report thetiming difference based at least in part on determining a change in thenumber of subframes impacted by the timing difference (e.g., based on apossible timing difference inaccuracy and/or subframe boundarymisalignment). Still in another example, as described, timing differencereporting component 652 can report the timing difference based at leastin part on detecting expiration of a prohibit timer that is initializedafter a previous report of the timing difference.

In an example, timing difference reporting component 652 may report thetiming difference in a radio resource control (RRC) message to theMeNodeB 605-a over the established connection therewith. In anotherexample, timing difference reporting component 652 may report the timingdifference to the SeNodeB 605-b in an RRC message over the establishedconnection therewith, or in a media access control (MAC) control element(CE) where RRC resources are not yet established, as described furtherherein. As described, the reported timing difference can include anumber of milliseconds, microseconds, subframes, SFNs, etc. between thetiming of the SeNodeB 605-b and the MeNodeB 605-a, such that at leastone of the SeNodeB 605-b and/or MeNodeB 605-a can determine one or moresubframes that substantially align to subframes of the other eNodeB. Ineither case, as described further herein, the SeNodeB 605-b can utilizethe timing difference and known timing information of certain operationsof the MeNodeB 605-a (e.g., measurement gaps, DRX-on durations, etc.) toschedule communications with the UE 615 over communication link 625-b.In addition, in one example, timing difference reporting component 652may report the timing difference based on one or more of the triggersdescribed above. It is to be appreciated that timing differencedetermining component 650 may determine the timing difference accordingto one trigger (e.g., periodic timer) or parameter(s) specified in thereporting configuration, and timing difference reporting component 652may report the timing difference based on another trigger orparameter(s) specified in the reporting configuration (e.g., based oncomparing a difference between the timing difference and an assumedtiming difference, previous timing difference, etc. to one or morethresholds).

Method 800 also optionally includes, at 820, receiving resourcesscheduled based at least in part on the reported timing difference.Communicating component 640 can receive resources scheduled based atleast in part on the reported timing difference. As described above andfurther herein, SeNodeB 605-b can schedule resources for the UE 615 toperform one or more operations based on resources (e.g., subframes)scheduled for the UE 615 by MeNodeB 605-a to perform the operationsadjusted by the reported timing difference (e.g., and/or includingadditional resources based on an inaccuracy of the reported timingdifference).

FIG. 9 illustrates an example method 900 for suspending configuringaspects of a second connection with a second cell until the timingdifference is reported. Method 900 includes, at Block 910, establishinga first connection served by at least a first cell. Communicatingcomponent 640 (FIG. 6) can establish the first connection served by atleast the first cell, which can include communication link 625-a withMeNodeB 605-a. Method 900 also includes, at Block 912, receiving aconfiguration message to configure a second connection served by atleast a second cell. Communicating component 640 can also receive theconfiguration message to configure the second connection served by atleast the second cell. For example, the configuration message mayinclude a connection reconfiguration message (e.g., an RRC ConnectionReconfiguration message) or similar message received at an RRC layer orother network layer that facilitates configuring or otherwiseestablishing a radio connection between the UE 602 and an eNodeB (e.g.,SeNodeB 605-b) or related cell. As described previously, the connectionscan be configured using multiple connectivity to provide the UE 615 withcommunications configured in an MCG and SCG. Configuring of the secondconnection, however, can be delayed until after a timing differencebetween the MeNodeB 605-a and SeNodeB 605-b is reported, such thatconfiguring the second connection is based not only on receiving theconfiguration message but also on reporting the timing difference.

Method 900 also includes, at Block 914, determining a timing differencebetween at least the first cell and at least the second cell. Forexample, timing difference determining component 650 can determine thetiming difference between a cell or cell group of MeNodeB 605-a and acell or cell group of SeNodeB 605-b, as described with reference to FIG.8 (e.g., and/or based on one or more triggers detected by timingdifference triggering component 654). Method 900 also includes, at Block916, reporting the timing difference to at least the first cell over thefirst connection. For example, timing difference reporting component 652can report the timing difference, as described with reference to FIG. 8(e.g., and/or based on one or more triggers detected by timingdifference triggering component 654).

Method 900 also includes, at Block 918, configuring the secondconnection served by at least the second cell based at least in part onreporting the timing difference to at least the first cell. Connectionconfiguring component 656 can configure the second connection (e.g.,communication link 625-b) served by at least the second cell (e.g., acell or cell group of SeNodeB 605-b) based at least in part on reportingthe timing difference to at least the first cell (e.g., timingdifference reporting component 652 reporting the timing difference to acell or cell group of MeNodeB 605-a). Thus, for example, connectionconfiguring component 656 can delay one or more aspects of configuringcommunications over the communication link 625-b (e.g., based onreceiving the configuration message) until the timing difference isreported, until a response to reporting the timing difference isreceived (e.g., from MeNodeB 605-a), etc. In one example, connectionconfiguring component 656 can delay establishment or configuring of theconnection based on the received request to establish a connection untilthe timing difference is reported by timing difference reportingcomponent 652.

In another example, communicating component 640 may have received ameasurement gap configuration, DRX configuration, or similarconfigurations for communicating with MeNodeB 605-a. In this example,connection configuring component 656 can suspend such configurations (orrelated operations) at MeNodeB 605-a until timing difference reportingcomponent 652 reports the timing difference between MeNodeB 605-a andSeNodeB 605-b (or between the related connections). In this regard,SeNodeB 605-b can determine the timing difference, and accordinglyconfigure measurement gaps, DRX-on durations, etc. for communicationlink 625-b, as described (and thus connection configuring component 656can resume the configurations once timing difference is reported or oncea configuration of timing difference receipt is received). In oneexample, suspending the configurations in this regard can be based atleast in part on receiving an indication from the network (e.g., MeNodeB605-a or another network entity) to suspend the configurations untiltiming difference is reported. In yet another example, MeNodeB 605-a candeconfigure the configurations (e.g., the measurement gap configuration,DRX configuration, etc.) at the UE 615 until the timing difference isreported from the UE 615.

FIG. 10 is a block diagram 1000 conceptually illustrating an example ofa network entity 1005-a and components configured in accordance with anaspect of the present disclosure. FIGS. 11 and 12, which are describedin conjunction with FIG. 10 herein, illustrate example methods 1100 and1200 in accordance with aspects of the present disclosure. Although theoperations described below in FIGS. 11 and 12 are presented in aparticular order and/or as being performed by an example component, itshould be understood that the ordering of the actions and the componentsperforming the actions may be varied, depending on the implementation.Moreover, it should be understood that the following actions orfunctions may be performed by a specially-programmed processor, aprocessor executing specially-programmed software or computer-readablemedia, or by any other combination of a hardware component and/or asoftware component capable of performing the described actions orfunctions.

Referring to FIG. 10, diagram 1000 includes network entities 1005-a,1005-b, which can include one or more previously described basestations/eNodeBs (e.g., MeNodeB 605-a that provides a PCell_(MCG),SeNodeB that provides a PCell_(SCG), etc.), or other network entities,along with a UE 1015, which can include one or more previously describedUEs (e.g., UE 615). The network entity 1005-a and the UE 1015 maycommunicate over communication link 1025-a, network entity 1005-b and UE1015 may communicate over communication link 1025-b, and networkentities 1005-a and 1005-b may communicate over a backhaul link 1034. UE1015 may be configured to determine and report a timing differencebetween the network entity 1005-a and network entity 1005-b (and/orother network entities), as described herein. Network entity 1005-aincludes a communicating component 1040 for obtaining and utilizing atiming difference report received from a UE in scheduling communicationsfor the UE. It is to be appreciated that network entity 1005-b may alsoinclude a communicating component 1040 and/or components thereof toperform the functions described herein, but these components are omittedfor ease of explanation.

Communicating component 1040 can include, or can be in communicationwith, a timing difference receiving component 1050 for receiving atiming difference between the network entity 1005-a and another networkentity from a UE, and a connection configuring component 1052 forconfiguring a connection with the UE based at last in part on thereceived timing difference. Communicating component 1040 can optionallyinclude, or can be in communication with, a timing difference inaccuracydetermining component 1054 for determining a possible inaccuracy of areceived timing difference, and/or a timing difference triggeringcomponent 1056 for triggering timing difference reporting to the UE.

FIG. 11 illustrates an example method 1100 for configuringcommunications with a UE based on a received timing difference. Method1100 optionally includes, at Block 1110, sending information fortriggering timing difference reporting between two cells or cell groups.Timing difference triggering component 1056 (FIG. 10) can send theinformation for triggering timing difference reporting between two cellsor cell groups to UE 1015. For example, the information can include arequest for the UE 1015 to determine and report the timing differencebetween network entities 1005-a and 1005-b (or related cells or cellgroups), a type of trigger to detect for determining to determine and/orreport a timing difference between cells or cell groups, a periodictimer value according to which UE 1015 should determine and reporttiming difference, a threshold timing difference between networkentities 1005-a and 1005-b (or related cells or cell groups) that the UE1015 should report when achieved, a prohibit timer value to which UE1015 should adhere in reporting timing difference, and/or the like, asdescribed. In other examples, as described, the UE 1015 can determinethe trigger based on information configured at the UE 1015, in whichcase Block 1110 may not be included in the method 1100.

Method 1100 includes, at Block 1112, receiving a reported timingdifference determined by a UE. Timing difference receiving component1050 can receive the reported timing difference determined by UE 1015.For example, the timing difference can indicate a timing differencebetween network entities 1005-a and 1005-b (or related cells or cellgroups) over related communication links 1025-a and 1025-b, which may beexpressed as a duration in time computed based on system informationreceived from network entities 1005-a and 1005-b (e.g., a number ofmilliseconds or microseconds), start of a SFN or subframe correspondingto certain system times, etc. The reported timing difference can enablenetwork entity 1005-a to configure certain operations with the UE 1015such that the operations are substantially time aligned with similaroperations of network entity 1005-b based on the reported timingdifference. In an example, the timing difference report can be receivedfrom the UE 1015 and/or from another entity in the wireless network(e.g., network entity 1005-b over backhaul link 1034).

Method 1100 optionally includes, at Block 1114, determining a possibleinaccuracy of the timing difference reported by the UE. Timingdifference inaccuracy determining component 1054 can determine thepossible timing inaccuracy of the timing difference reported by the UE1015 (e.g., as received by timing difference receiving component 1050).For example, timing difference inaccuracy determining component 1054 candetermine the possible timing inaccuracy based on a class orconfiguration related to the UE 1015.

Method 1100 also includes, at Block 1116, configuring communicationswith the UE based at least in part on the timing difference and/or theinaccuracy. Connection configuring component 1052 can configure thecommunications with the UE 1015 (e.g., communication link 1025-a) basedat least in part on the timing difference (e.g., as reported by the UE1015 and received at timing difference receiving component 1050) and/orthe inaccuracy (e.g., as determined by timing difference inaccuracydetermining component 1054). Connection configuring component 1052 canalso configure the communications with UE 1015 based on resources (e.g.,subframes) configured by network entity 1005-b, which may be indicatedto network entity 1005-a via backhaul link 1034). As described, networkentity 1005-a can determine a possible inaccuracy in timing estimationperformed by UE 1015 according to a δ value, which can be configured atthe network entity 1005 based on a configuration, a type of UE 1015,etc. Timing difference inaccuracy determining component 1054 candetermine whether to consider this possible inaccuracy in evaluating thetiming difference received from the UE 1015 for configuringcommunications therewith via connection configuring component 1052.

In one example, the timing inaccuracy expected for the UE 1015 may besmall such that the timing difference reported by the UE 1015 isexpected to have high accuracy (e.g., less than half a symbol ofpossible inaccuracy). In this example, and where network entities 1005-aand 1005-b are aligned in subframe boundary (e.g., in example 1described in timing difference 700 of FIG. 7), connection configuringcomponent 1052 can configure the connection with the UE 1015 based onrounding the reported timing difference to the next or previous subframelength multiple (e.g., which ever results in the lesser difference valuebetween the reported timing difference and the rounded timingdifference) and adjusting for the number of subframes indicated by thetiming difference. In this regard, connection configuring component 1052can configure the connection with the UE 1015 to use a same number ofsubframes for certain operations (e.g., measurement gaps, DRX-onduration, etc.) that are aligned to those used by the other eNodeBwithout including additional subframes.

In another example, the timing inaccuracy expected for the UE 1015 maybe larger such that the timing difference reported by the UE 1015 maynot be as accurate (e.g., having more than half a symbol of possibleinaccuracy), and the timing difference may indicate a misalignment insubframe boundaries (e.g., where the timing difference modulo thesubframe length is greater than a threshold). In this example, timingdifference inaccuracy determining component 1054 may consider possibleinaccuracy in the timing difference reported by the UE 1015 (e.g., as inexamples 2 and 3 in timing differences 702 and 704 in FIG. 7). Forexample, timing difference inaccuracy determining component 1054 canobtain a maximum possible inaccuracy, and can determine whether thetiming difference received from the UE 1015 indicates a subframeboundary offset that is within the possible inaccuracy or not. Forexample, as described, timing difference inaccuracy determiningcomponent 1054 can determine whether the subframe boundary offset (e.g.,the received timing offset modulo the subframe length) is greater thanthe inaccuracy δ and less than 1−δ. In this case, the subframe boundaryoffset is not within the inaccuracy δ, and connection configuringcomponent 1052 can determine whether the network entity 1005-a is aheador behind the network entity 1005-b in timing, and thus whether toschedule an additional subframe at the beginning or end of theconfigured subframes, respectively, for one or more operations (e.g.,measurement gap, DRX, etc.) in aligning with the network entity 1005-b,as described. Where timing difference inaccuracy determining component1054 determines that the subframe boundary offset is less than theinaccuracy δ or greater than 1−δ, this indicates the subframe boundaryoffset is within the δ, and connection configuring component 1052 canschedule an additional subframe at the beginning and an additionalsubframe at the end of the configured subframes for one or moreoperations (e.g., measurement gap, DRX, etc.) in aligning with the othereNodeB, as described.

FIG. 12 illustrates an example method 1200 for configuringcommunications with a UE based on a received timing difference. Method1200 optionally includes, at Block 1210, establishing a first connectionwith a UE in a first cell. Communicating component 1040 can establishthe first connection (e.g., communication link 1025-a) with the UE 1015in the first cell (which may include a cell or cell group provided bynetwork entity 1005-a). It is to be appreciated, in this example, thatnetwork entity 1005-a may be the MeNodeB. Method 1200 can also include,at Block 1212, transmitting a configuration message to the UE toestablish a second connection in a second cell. Communicating component1040 can also send the configuration message to the UE 1015 to establishanother connection with the second cell, which may be provided bynetwork entity 1005-b (e.g., a SeNodeB).

As described, for example, receiving the configuration at the UE 1015can cause the UE 1015 to determine a timing difference between the firstand second cell to facilitate time aligning of certain operations at thecells (e.g., measurement gaps, DRX durations, etc.). Thus, method 1200also includes, at Block 1214, configuring the second connection based atleast in part on receiving a timing difference between the first celland the second cell reported by the UE. Connection configuring component1052 can configure the connection based at least in part on receivingthe timing difference. For example, connection configuring component1052 can suspend measurement gaps, DRX durations, and related operationsbetween transmitting the configuration message to the UE 1015 andreceiving the timing difference report from the UE 1015. In anotherexample, configuring the connection can include providing the timingdifference information to the network entity 1005-b (e.g., via backhaullink 1034) to allow the network entity 1005-b to establish theconnection with the UE 1015 and schedule certain operations, such asmeasurement gaps, DRX durations, etc., such to align timing thereof withthe network entity 1005-a based on the timing difference (e.g., asdescribed in reference to FIG. 11).

FIG. 13 is a block diagram conceptually illustrating an example hardwareimplementation for an apparatus 1300 employing a processing system 1314configured in accordance with an aspect of the present disclosure. Theprocessing system 1314 includes a communicating component 1340. In oneexample, the apparatus 1300 may be the same or similar, or may beincluded with one of the UEs, eNodeBs, network entities, etc. describedin various Figures. In such example, the communicating component 1340may correspond to, for example, the communicating component 640 of UE615, communicating component 1040 of network entity 1005-a, etc., andmay thus include or otherwise be coupled to the components thereof toprovide the functions described herein. In this example, the processingsystem 1314 may be implemented with a bus architecture, representedgenerally by the bus 1302. The bus 1302 may include any number ofinterconnecting buses and bridges depending on the specific applicationof the processing system 1314 and the overall design constraints. Thebus 1302 links together various circuits including one or moreprocessors (e.g., central processing units (CPUs), microcontrollers,application specific integrated circuits (ASICs), field programmablegate arrays (FPGAs)) represented generally by the processor 1304, andcomputer-readable media, represented generally by the computer-readablemedium 1306. The bus 1302 may also link various other circuits such astiming sources, peripherals, voltage regulators, and power managementcircuits, which are well known in the art, and therefore, will not bedescribed any further. A bus interface 1308 provides an interfacebetween the bus 1302 and a transceiver 1310, which is connected to oneor more antennas 1320 for receiving or transmitting signals. Thetransceiver 1310 and the one or more antennas 1320 provide a mechanismfor communicating with various other apparatus over a transmissionmedium (e.g., over-the-air). Depending upon the nature of the apparatus,a user interface (UI) 1312 (e.g., keypad, display, speaker, microphone,joystick) may also be provided.

The processor 1304 is responsible for managing the bus 1302 and generalprocessing, including the execution of software stored on thecomputer-readable medium 1306. The software, when executed by theprocessor 1304, causes the processing system 1314 to perform the variousfunctions described herein for any particular apparatus. Thecomputer-readable medium 1306 may also be used for storing data that ismanipulated by the processor 1304 when executing software. Thecommunicating component 1340 as described above may be implemented inwhole or in part by processor 1304, or by computer-readable medium 1306,or by any combination of processor 1304 and computer-readable medium1306.

Those of skill in the art would understand that information and signalsmay be represented using any of a variety of different technologies andtechniques. For example, data, instructions, commands, information,signals, bits, symbols, and chips that may be referenced throughout theabove description may be represented by voltages, currents,electromagnetic waves, magnetic fields or particles, optical fields orparticles, or any combination thereof.

Those of skill would further appreciate that the various illustrativelogical blocks, modules, circuits, and algorithm steps described inconnection with the disclosure herein may be implemented as electronichardware, computer software, or combinations of both. To clearlyillustrate this interchangeability of hardware and software, variousillustrative components, blocks, modules, circuits, and steps have beendescribed above generally in terms of their functionality. Whether suchfunctionality is implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem. Skilled artisans may implement the described functionality invarying ways for each particular application, but such implementationdecisions should not be interpreted as causing a departure from thescope of the present disclosure.

The various illustrative logical blocks, modules, and circuits describedin connection with the disclosure herein may be implemented or performedwith a general-purpose processor, a digital signal processor (DSP), anASIC, an FPGA or other programmable logic device, discrete gate ortransistor logic, discrete hardware components, or any combinationthereof designed to perform the functions described herein. Ageneral-purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

The steps of a method or algorithm described in connection with thedisclosure herein may be embodied directly in hardware, in a softwaremodule executed by a processor, or in a combination of the two. Asoftware module may reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of storage medium known in the art. Anexemplary storage medium is coupled to the processor such that theprocessor can read information from, and write information to, thestorage medium. In the alternative, the storage medium may be integralto the processor. The processor and the storage medium may reside in anASIC. The ASIC may reside in a user terminal. In the alternative, theprocessor and the storage medium may reside as discrete components in auser terminal.

In one or more exemplary designs, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored on ortransmitted over as one or more instructions or code on acomputer-readable medium. Computer-readable media includes both computerstorage media and communication media including any medium thatfacilitates transfer of a computer program from one place to another. Astorage media may be any available media that can be accessed by ageneral purpose or special purpose computer. By way of example, and notlimitation, such computer-readable media can comprise RAM, ROM, EEPROM,CD-ROM or other optical disk storage, magnetic disk storage or othermagnetic storage devices, or any other medium that can be used to carryor store desired program code means in the form of instructions or datastructures and that can be accessed by a general-purpose orspecial-purpose computer, or a general-purpose or special-purposeprocessor. Also, any connection is properly termed a computer-readablemedium. For example, if the software is transmitted from a website,server, or other remote source using a coaxial cable, fiber optic cable,twisted pair, digital subscriber line (DSL), or wireless technologiessuch as infrared, radio, and microwave, then the coaxial cable, fiberoptic cable, twisted pair, DSL, or wireless technologies such asinfrared, radio, and microwave are included in the definition of medium.Disk and disc, as used herein, includes compact disc (CD), laser disc,optical disc, digital versatile disc (DVD), floppy disk and Blu-ray discwhere disks usually reproduce data magnetically, while discs reproducedata optically with lasers. Combinations of the above should also beincluded within the scope of computer-readable media.

The previous description of the disclosure is provided to enable anyperson skilled in the art to make or use the disclosure. Variousmodifications to the disclosure will be readily apparent to thoseskilled in the art, and the generic principles defined herein may beapplied to other variations without departing from the spirit or scopeof the disclosure. Thus, the disclosure is not intended to be limited tothe examples and designs described herein, but it is to be accorded thewidest scope consistent with the principles and novel features disclosedherein.

What is claimed is:
 1. A method for reporting difference in timingbetween cells using multiple connectivity in a wireless network,comprising: establishing a first connection served by at least a firstcell, the first connection is established with a master cell groupincluding at least the first cell as a primary cell of the master cellgroup; establishing a second connection served by at least a secondcell, the second connection is established with a secondary cell groupincluding at least the second cell as a primary cell of the secondarycell group; receiving, from at least one of the first cell or the secondcell, a reporting configuration specifying one or more parametersrelated to reporting a timing difference between at least the first celland at least the second cell, wherein the one or more parameters includea request to report an offset in subframe alignment between at least thefirst cell as the primary cell of the master cell group and at least thesecond cell as the primary cell of the secondary cell group;determining, based at least in part on receiving the request, the timingdifference between at least the first cell and at least the second cell;reporting, based at least in part on receiving the request, the timingdifference as the offset in subframe alignment to at least the firstcell over the first connection or to at least the second cell over thesecond connection; receiving, from the first cell, scheduling of firstresources for performing one or more first operations; and receiving,from the second cell, scheduling of second resources for performing oneor more second operations, wherein the second resources are adjustedbased at least in part on the timing difference as reported.
 2. Themethod of claim 1, wherein reporting the timing difference is based atleast in part on detecting expiration of a periodic timer, wherein theone or more parameters relate to the periodic timer.
 3. The method ofclaim 1, wherein reporting the timing difference is based at least inpart on determining that the timing difference differs from an assumedtiming difference by at least a threshold, wherein the one or moreparameters relate to the assumed timing difference or the threshold. 4.The method of claim 1, wherein reporting the timing difference is basedat least in part on determining that the timing difference differs froma previously reported timing difference by at least a threshold, whereinthe one or more parameters relate to the threshold.
 5. The method ofclaim 1, wherein reporting the timing difference is based at least inpart on determining that the timing difference corresponds to the offsetin subframe alignment that is outside of a range corresponding to apossible timing accuracy where a previously reported timing differencecorresponded to a previous offset in subframe alignment that was insideof the range corresponding to the possible timing accuracy.
 6. Themethod of claim 1, wherein reporting the timing difference is based atleast in part on determining that the timing difference corresponds tothe offset in subframe alignment that is inside of a range correspondingto a possible timing accuracy where a previously reported timingdifference corresponded to a previous offset in subframe alignment thatwas outside of the range corresponding to the possible timing accuracy.7. The method of claim 1, wherein reporting the timing difference isbased at least in part on detecting expiration of a prohibit timer. 8.The method of claim 1, further comprising configuring one or moreadditional parameters for communicating over the first connection or thesecond connection based at least in part on the timing difference. 9.The method of claim 8, wherein the one or more additional parameterscorrespond to measurement gaps defined for the first connection or thesecond connection.
 10. The method of claim 1, further comprisingreceiving a connection reconfiguration message to configure the secondconnection served by at least the second cell, wherein reporting thetiming difference is based at least in part on receiving the reportingconfiguration, and wherein establishing the second connection includesconfiguring the second connection based at least in part on receivingthe connection reconfiguration message and reporting the timingdifference.
 11. An apparatus for reporting difference in timing betweencells using multiple connectivity in a wireless network, comprising: amemory; and at least one processor coupled to the memory, wherein the atleast one processor is configured to: establish a first connectionserved by at least a first cell, the first connection is establishedwith a master cell group including at least the first cell as a primarycell of the master cell group; establish a second connection served byat least a second cell to facilitate communicating with at least thefirst cell and at least the second cell, the second connection isestablished with a secondary cell group including at least the secondcell as a primary cell of the secondary cell group; receive, from atleast one of the first cell or the second cell, a reportingconfiguration specifying one or more parameters related to reporting atiming difference between at least the first cell and at least thesecond cell, wherein the one or more parameters include a request toreport an offset in subframe alignment between at least the first cellas the primary cell of the master cell group and at least the secondcell as the primary cell of the secondary cell group; determine, basedat least in part on receiving the request, the timing difference betweenat least the first cell and at least the second cell; and report, basedat least in part on receiving the request, the timing difference as theoffset in subframe alignment to at least the first cell over the firstconnection or to at least the second cell over the second connection;receive, from the first cell, scheduling of first resources forperforming one or more first operations; and receive, from the secondcell, scheduling of second resources for performing one or more secondoperations, wherein the second resources are adjusted based at least inpart on the timing difference as reported.
 12. The apparatus of claim11, wherein the at least one processor is configured to report thetiming difference based at least in part on detecting expiration of aperiodic timer, wherein the one or more parameters relate to theperiodic timer.
 13. The apparatus of claim 11, wherein the at least oneprocessor is configured to report the timing difference based at leastin part on determining that the timing difference differs from anassumed timing difference by at least a threshold, wherein the one ormore parameters relate to the assumed timing difference or thethreshold.
 14. The apparatus of claim 11, wherein the at least oneprocessor is configured to report the timing difference based at leastin part on determining that the timing difference differs from apreviously reported timing difference by at least a threshold, whereinthe one or more parameters relate to the threshold.
 15. The apparatus ofclaim 11, wherein the at least one processor is configured to report thetiming difference based at least in part on determining that the timingdifference corresponds to the offset in subframe alignment that isoutside of a range corresponding to a possible timing accuracy where apreviously reported timing difference corresponded to a previous offsetin subframe alignment that was inside of the range corresponding to thepossible timing accuracy.
 16. The apparatus of claim 11, wherein the atleast one processor is configured to report the timing difference basedat least in part on determining that the timing difference correspondsto the offset in subframe alignment that is inside of a rangecorresponding to a possible timing accuracy where a previously reportedtiming difference corresponded to a previous offset in subframealignment that was outside of the range corresponding to the possibletiming accuracy.
 17. The apparatus of claim 11, wherein the at least oneprocessor is configured to report the timing difference based at leastin part on detecting expiration of a prohibit timer.
 18. The apparatusof claim 11, wherein the at least one processor is further configured toconfigure one or more additional parameters for communicating over thefirst connection or the second connection based at least in part on thetiming difference.
 19. The apparatus of claim 18, wherein the one ormore additional parameters correspond to measurement gaps defined forthe first connection or the second connection.
 20. The apparatus ofclaim 11, wherein the at least one processor is further configured toreceive a connection reconfiguration message to configure the secondconnection served by at least the second cell, report the timingdifference based at least in part on receiving the reportingconfiguration, and establish the second connection at least in part byconfiguring the second connection based at least in part on receivingthe connection reconfiguration message and reporting the timingdifference.
 21. An apparatus for reporting difference in timing betweencells using multiple connectivity in a wireless network, comprising:means for establishing a first connection served by at least a firstcell, the first connection is established with a master cell groupincluding at least the first cell as a primary cell of the master cellgroup; means for establishing a second connection served by at least asecond cell to facilitate communicating with at least the first cell andat least the second cell, the second connection is established with asecondary cell group including at least the second cell as a primarycell of the secondary cell group; means for receiving, from at least oneof the first cell or the second cell, a reporting configurationspecifying one or more parameters related to reporting a timingdifference between at least the first cell and at least the second cell,wherein the one or more parameters include a request to report an offsetin subframe alignment between at least the first cell as the primarycell of the master cell group and at least the second cell as theprimary cell of the secondary cell group; means for determining, basedat least in part on receiving the request, the timing difference betweenat least the first cell and at least the second cell; means forreporting, based at least in part on receiving the request, the timingdifference as the offset in subframe alignment to at least the firstcell over the first connection or to at least the second cell over thesecond connection; means for receiving, from the first cell, schedulingof first resources for performing one or more first operations; andmeans for receiving, from the second cell, scheduling of secondresources for performing one or more second operations, wherein thesecond resources are adjusted based at least in part on the timingdifference as reported.
 22. The apparatus of claim 21, wherein the meansfor reporting reports the timing difference based at least in part ondetecting expiration of a periodic timer, wherein the one or moreparameters relate to the periodic timer.
 23. The apparatus of claim 21,wherein the means for reporting reports the timing difference based atleast in part on determining that the timing difference differs from theassumed timing difference by at least a threshold, wherein the one ormore parameters relate to the threshold.
 24. A non-transitorycomputer-readable storage medium comprising computer-executable code forreporting difference in timing between cells using multiple connectivityin a wireless network, the code comprising: code for establishing afirst connection served by at least a first cell, the first connectionis established with a master cell group including at least the firstcell as a primary cell of the master cell group; code for establishing asecond connection served by at least a second cell to facilitatecommunicating with at least the first cell and at least the second cell,the second connection is established with a secondary cell groupincluding at least the second cell as a primary cell of the secondarycell group; code for receiving, from at least one of the first cell orthe second cell, a reporting configuration specifying one or moreparameters related to reporting a timing difference between at least thefirst cell and at least the second cell, wherein the one or moreparameters include a request to report an offset in subframe alignmentbetween at least the first cell as the primary cell of the master cellgroup and at least the second cell as the primary cell of the secondarycell group; code for determining, based at least in part on receivingthe request, the timing difference between at least the first cell andat least the second cell; code for reporting, based at least in part onreceiving the request, the timing difference as the offset in subframealignment to at least the first cell over the first connection or to atleast the second cell over the second connection; code for receiving,from the first cell, scheduling of first resources for performing one ormore first operations; and code for receiving, from the second cell,scheduling of second resources for performing one or more secondoperations, wherein the second resources are adjusted based at least inpart on the timing difference as reported.
 25. The non-transitorycomputer-readable storage medium of claim 24, wherein the code forreporting reports the timing difference based at least in part ondetecting expiration of a periodic timer, wherein the one or moreparameters relate to the periodic timer.
 26. The non-transitorycomputer-readable storage medium of claim 24, wherein the code forreporting reports the timing difference based at least in part ondetermining that the timing difference differs from the assumed timingdifference by at least a threshold, wherein the one or more parametersrelate to the threshold.